Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1687

reference: 263-tree-1
name: 1687
tree-preservation-order: undefined
263-tpo-1
uprn: 10013678141
address-text: 12-14 Leigh Road, Havant
point: POINT (-0.978907 50.856923)
geometry: MULTIPOLYGON (((-0.978822 50.856914,-0.978826 50.856930,-0.978838 50.856945,-0.978856 50.856958,-0.978880 50.856965,-0.978906 50.856968,-0.978933 50.856966,-0.978957 50.856958,-0.978976 50.856947,-0.978988 50.856932,-0.978993 50.856915,-0.978989 50.856898,-0.978977 50.856883,-0.978959 50.856871,-0.978935 50.856863,-0.978909 50.856860,-0.978882 50.856863,-0.978858 50.856870,-0.978839 50.856882,-0.978827 50.856897,-0.978822 50.856914)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL